© 2021 Ribbon Communications Operating Company, Inc. © 2021 ECI Telecom Ltd. All rights reserved. The compilation (meaning the collection, arrangement and assembly) of all content on this site is protected by U.S. and international copyright laws and treaty provisions and may not be used, copied, reproduced, modified, published, uploaded, posted, transmitted or distributed in any way, without prior written consent of Ribbon Communications Inc.
The trademarks, logos, service marks, trade names, and trade dress (“look and feel”) on this website, including without limitation the RIBBON and RIBBON logo marks, are protected by applicable US and foreign trademark rights and other proprietary rights and are the property of Ribbon Communications Operating Company, Inc. or its affiliates. Any third-party trademarks, logos, service marks, trade names and trade dress may be the property of their respective owners. Any uses of the trademarks, logos, service marks, trade names, and trade dress without the prior written consent of Ribbon Communications Operating Company, Inc., its affiliates, or the third parties that own the proprietary rights, are expressly prohibited.
This document outlines the configuration best practices for Vodafone involving EdgeMarc 2900 when deployed with SwyxPBX. This document provides the configuration snapshot of the interoperability performed between Ribbon's EdgeMarc 2900 and SwyxPBX, SwyxIt and Swyx Phone. SwyxPBX is a fully “Hosted PBX Service” with cloud telephony. In cases when you no longer have a PBX in your company, you obtain all features as a service from the cloud but you can keep your existing contract with your Service Provider who will provide you a local breakout.
This document provides configuration best practices for deploying Ribbon's EdgeMarc 2900 with SwyxPBX and associated users. Note that these are configuration best practices and each customer may have unique needs and networks. Ribbon recommends that customers work with network design and deployment engineers to establish the network design which best meets their requirements.
It is not the goal of this document to provide detailed configurations that will meet the requirements of every customer. Use this document as a starting point and build the SBC configurations in consultation with network design and deployment engineers.
This is a technical document is intended for telecommunications engineers with the purpose of configuring both the Ribbon EdgeMarc 2900 and the SwyxPBX and associated users.
Steps will require navigating the third-party product as well as the Ribbon product using graphical user interface (GUI) or command line interface (CLI). An understanding of the basic concepts of TCP/UDP/TLS, IP/Routing, and SIP/RTP/SRTP is needed to complete the configuration and any necessary troubleshooting.
The following aspects would be required before proceeding with Ribbon EM 2900 POE & SwyxWare 12.10.
SwyxWare 12.10 is installed in a Windows Server Platform and connected to the network.
Remote Desktop access to Windows host is available for remote access and configuration.
A valid 6 months trial License is running on the Server.
Equipment/Product | Software Version | |
---|---|---|
Ribbon Communications | EdgeMarc 2900 POE | Version 15.8.3 |
Third-Party Products | SwyxWare | V12.10.16296.0 |
SwyxIt | V12.10.16296 | |
Windows Server | 2019 | |
Unify CP205 | V1 R3.9.0 HFA 190516 |
The deployment topology diagram is depicted below.
IOT high-level architecture covering call flows & overall topology is depicted below.
In this use case, EdgeMarc A has a simple VPN configuration with no SIP configuration.
EdgeMarc B is responsible for communicating with the SIP Service Provider as well as passing HFA phone traffic via IPSec tunnel to the head-end PBX. Configure IPSec:
The Protected Remote network - voice VLAN of EdgeMarc A.
In addition, a static route is required on EdgeMarc B to allow the ALG to function correctly when communicating to a SIP PBX across a VPN tunnel. After logging into the EdgeMarc, execute the following commands:
echo "router add -net 192.168.8.0/24 gw 172.16.1.1" >> /etc/config/user_defs.conf cfg_commit config_network
The Unify CP 205 comes out of the box as a SIP Phone. You must upgrade the firmware before configuring HFA Phone. Upgrade the firmware using FTP/HTTPS Access Data
By default, the phone has DHCP enabled. Look on the EdgeMarc 2900 for the IP leased to the CP205 unit.
The following checklist identifies the set of supplementary services/features covered through the configuration defined in this Interop document.
Sr. No. | Supplementary Services/Features | Coverage |
---|---|---|
1 | Registration over UDP/TCP/TLS | |
2 | Basic Call Setup & Termination | |
3 | Ringing & Local Ringback Tone | |
4 | Remote Ringback Tone Handling | |
5 | Cancel Call & Call Rejection | |
6 | Call Forwarding Busy | |
7 | Call Forward No Answer | |
8 | Call Transfer (Attended) | |
9 | Call Transfer (Blind/ Unattended) | |
10 | Conference Call |
Legend
Supported | |
Not Supported |
The following items should be noted in relation to this Interop document. These are either limitations, untested elements, or useful information pertaining to the Interoperability.
For any support related queries about this guide, please contact your local Ribbon representative, or use the details below:
For detailed information about Ribbon products & solutions, please visit:
https://ribboncommunications.com/products
This Interoperability document describes a successful configuration and interop involving EdgeMarc 2900 and SwyxWare PBX.
All features and capabilities tested are detailed within this document. Any limitations, notes or observations are also recorded to provide the reader with an accurate understanding of what has been covered, and what has not.
Configuration guidance is provided to enable the reader to replicate the same base setup - there maybe additional configuration changes required to suit the exact deployment environment.
© 2021 Ribbon Communications Operating Company, Inc. © 2021 ECI Telecom Ltd. All rights reserved.